v2.0.1

Compare Source

v5.10.2

Compare Source

Bug Fixes

• eslint-plugin: [no-restricted-imports] allow relative type imports with patterns configured (#​4494) (4a6d217)

v5.10.2

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v10.2.4

Compare Source

v10.2.3

Compare Source

v10.2.2

Compare Source

v3.21.0

Compare Source

• Added Base64 utility methods:
  • atob
  • btoa
• Added the proper validation of arguments to some methods from web standards
• Forced replacement of all features from early-stage proposals for avoiding possible web compatibility issues in the future
• Added Rhino 1.7.14 compat data
• Added Deno 1.19 compat data mapping
• Added Opera Android 66 and 67 compat data mapping
• Added iOS Safari 15.3 and 15.4 compat data mapping

v0.14.16

Compare Source

• Support property name mangling with some TypeScript syntax features

  The newly-released --mangle-props= feature previously only affected JavaScript syntax features. This release adds support for using mangle props with certain TypeScript syntax features:

  • TypeScript parameter properties

    Parameter properties are a TypeScript-only shorthand way of initializing a class field directly from the constructor argument list. Previously parameter properties were not treated as properties to be mangled. They should now be handled correctly:

    // Original code
    class Foo {
      constructor(public foo_) {}
    }
    new Foo().foo_;
    
    // Old output (with --minify --mangle-props=_)
    class Foo{constructor(c){this.foo_=c}}new Foo().o;
    
    // New output (with --minify --mangle-props=_)
    class Foo{constructor(o){this.c=o}}new Foo().c;

  • TypeScript namespaces

    Namespaces are a TypeScript-only way to add properties to an object. Previously exported namespace members were not treated as properties to be mangled. They should now be handled correctly:

    // Original code
    namespace ns {
      export let foo_ = 1;
      export function bar_(x) {}
    }
    ns.bar_(ns.foo_);
    
    // Old output (with --minify --mangle-props=_)
    var ns;(e=>{e.foo_=1;function t(a){}e.bar_=t})(ns||={}),ns.e(ns.o);
    
    // New output (with --minify --mangle-props=_)
    var ns;(e=>{e.e=1;function o(p){}e.t=o})(ns||={}),ns.t(ns.e);

• Fix property name mangling for lowered class fields

  This release fixes a compiler crash with --mangle-props= and class fields that need to be transformed to older versions of JavaScript. The problem was that doing this is an unusual case where the mangled property name must be represented as a string instead of as a property name, which previously wasn't implemented. This case should now work correctly:

  // Original code
  class Foo {
    static foo_;
  }
  Foo.foo_ = 0;
  
  // New output (with --mangle-props=_ --target=es6)
  class Foo {
  }
  __publicField(Foo, "a");
  Foo.a = 0;

v0.14.15

Compare Source

• Add property name mangling with --mangle-props= (#​218)

  ⚠️ Using this feature can break your code in subtle ways. Do not use this feature unless you know what you are doing, and you know exactly how it will affect both your code and all of your dependencies. ⚠️

  This release introduces property name mangling, which is similar to an existing feature from the popular UglifyJS and Terser JavaScript minifiers. This setting lets you pass a regular expression to esbuild to tell esbuild to automatically rename all properties that match this regular expression. It's useful when you want to minify certain property names in your code either to make the generated code smaller or to somewhat obfuscate your code's intent.

  Here's an example that uses the regular expression _$ to mangle all properties ending in an underscore, such as foo_:

  $ echo 'console.log({ foo_: 0 }.foo_)' | esbuild --mangle-props=_$
  console.log({ a: 0 }.a);
  

  Only mangling properties that end in an underscore is a reasonable heuristic because normal JS code doesn't typically contain identifiers like that. Browser APIs also don't use this naming convention so this also avoids conflicts with browser APIs. If you want to avoid mangling names such as __defineGetter__ you could consider using a more complex regular expression such as [^_]_$ (i.e. must end in a non-underscore followed by an underscore).

  This is a separate setting instead of being part of the minify setting because it's an unsafe transformation that does not work on arbitrary JavaScript code. It only works if the provided regular expression matches all of the properties that you want mangled and does not match any of the properties that you don't want mangled. It also only works if you do not under any circumstances reference a property name to be mangled as a string. For example, it means you can't use Object.defineProperty(obj, 'prop', ...) or obj['prop'] with a mangled property. Specifically the following syntax constructs are the only ones eligible for property mangling:

  Syntax	Example
  Dot property access	x.foo_
  Dot optional chain	x?.foo_
  Object properties	x = { foo_: y }
  Object methods	x = { foo_() {} }
  Class fields	class x { foo_ = y }
  Class methods	class x { foo_() {} }
  Object destructuring binding	let { foo_: x } = y
  Object destructuring assignment	({ foo_: x } = y)
  JSX element names	<X.foo_></X.foo_>
  JSX attribute names	<X foo_={y} />

  You can avoid property mangling for an individual property by quoting it as a string. However, you must consistently use quotes or no quotes for a given property everywhere for this to work. For example, print({ foo_: 0 }.foo_) will be mangled into print({ a: 0 }.a) while print({ 'foo_': 0 }['foo_']) will not be mangled.

  When using this feature, keep in mind that property names are only consistently mangled within a single esbuild API call but not across esbuild API calls. Each esbuild API call does an independent property mangling operation so output files generated by two different API calls may mangle the same property to two different names, which could cause the resulting code to behave incorrectly.

  If you would like to exclude certain properties from mangling, you can reserve them with the --reserve-props= setting. For example, this uses the regular expression ^__.*__$ to reserve all properties that start and end with two underscores, such as __foo__:

  $ echo 'console.log({ __foo__: 0 }.__foo__)' | esbuild --mangle-props=_$
  console.log({ a: 0 }.a);
  
  $ echo 'console.log({ __foo__: 0 }.__foo__)' | esbuild --mangle-props=_$ "--reserve-props=^__.*__$"
  console.log({ __foo__: 0 }.__foo__);
  

• Mark esbuild as supporting node v12+ (#​1970)

  Someone requested that esbuild populate the engines.node field in package.json. This release adds the following to each package.json file that esbuild publishes:

  "engines": {
    "node": ">=12"
  },

  This was chosen because it's the oldest version of node that's currently still receiving support from the node team, and so is the oldest version of node that esbuild supports: https://nodejs.org/en/about/releases/.

• Remove error recovery for invalid // comments in CSS (#​1965)

  Previously esbuild treated // as a comment in CSS and generated a warning, even though comments in CSS use /* ... */ instead. This allowed you to run esbuild on CSS intended for certain CSS preprocessors that support single-line comments.

  However, some people are changing from another build tool to esbuild and have a code base that relies on // being preserved even though it's nonsense CSS and causes the entire surrounding rule to be discarded by the browser. Presumably this nonsense CSS ended up there at some point due to an incorrectly-configured build pipeline and the site now relies on that entire rule being discarded. If esbuild interprets // as a comment, it could cause the rule to no longer be discarded or even cause something else to happen.

  With this release, esbuild no longer treats // as a comment in CSS. It still warns about it but now passes it through unmodified. This means it's no longer possible to run esbuild on CSS code containing single-line comments but it means that esbuild's behavior regarding these nonsensical CSS rules more accurately represents what happens in a browser.

v8.8.0

Compare Source

Features

• 5d60812 feat: implement rfc 2021-suppression-support (#​15459) (Yiwei Ding)

Documentation

• 5769cc2 docs: fix relative link (#​15544) (Nick Schonning)
• ccbc35f docs: trimmed rules h1s to just be rule names (#​15514) (Josh Goldberg)
• 851f1f1 docs: fixed typo in comment (#​15531) (Jiapei Liang)
• 7d7af55 docs: address upcoming violation of markdownlint rule MD050/strong-style (#​15529) (David Anson)

v4.0.1

Compare Source

Changed

• Performance improvement: use resolve data already present in most modules
• Performance improvement: use throwIfNoEntry option on filesystem operations to improve performance

v14.0.0-next.1

Compare Source

Bug Fixes

• invalid browsers version ranges (547a11f)

v8.4.6

Compare Source

• Prevented comment removing when it change meaning of CSS.
• Fixed parsing space in last semicolon-less CSS Custom Properties.
• Fixed comment cleaning in CSS Custom Properties with space.
• Fixed throwing an error on .root access for plugin-less case.

v7.3.0

Compare Source

• Added @csstools/postcss-is-pseudo-class
  Check the plugin README for usage details.
• Added @csstools/postcss-hwb-function
  Check the plugin README for usage details.
• Added postcss-opacity-percentage
  Check the plugin README for usage details.
• Added postcss-clamp
  Check the plugin README for usage details.
• Added @csstools/postcss-normalize-display-values
  Check the plugin README for usage details.
• Added @csstools/postcss-font-format-keywords
  Check the plugin README for usage details.
• Added debug option that enables extra debugging information while processing the CSS.
• Added enableClientSidePolyfills option that allows you to control every single plugin that requires a browser library to fully work. Defaults to true so they're enabled by default.
• Added minimumVendorImplementations option that allows you to enable/disable plugins based on their implementation status in browsers.
• Fix sourcemaps for image-set() function.
• Removed caniuse-lite dependency. This results not only in lower package size but also in better feature detection lead by changes on CSSDB.
• Updated cssdb to 6.1.0 (major).
• Updated css-prefers-color-scheme to 6.0.3 (patch)
• Updated postcss-custom-properties to 12.1.4 (patch)
• Updated postcss-image-set-function to 4.0.5 (patch)
• Updated postcss-pseudo-class-any-link to 7.1.0 (minor)

v13.1.3

Compare Source

v1.49.7

Compare Source

Embedded Sass

• First stable release the sass-embedded npm package that contains the Node.js
  Embedded Host.

• First stable release of the sass_embedded pub package that contains the
  Embedded Dart Sass compiler.

v1.49.6

Compare Source

• No user-visible changes.

v1.49.5

Compare Source

• No user-visible changes.

v1.49.4

Compare Source

• No user-visible changes.

v1.49.3

Compare Source

• No user-visible changes.

v1.49.2

Compare Source

• No user-visible changes.

v1.49.1

Compare Source

• Stop supporting non-LTS Node.js versions.

v5.5.2

Compare Source

5.5.2 (2022-01-27)

Bug Fixes

• re-opening log files using SIGUSR2 (#​2966) (b964c0d) by @​marvinthepa

v5.68.0

Compare Source

Features

• allow to disable compile time evaluation of import.meta.url
• add __webpack_module__ and __webpack_module__.id to the api

Bugfixes

• fix handling of errors thrown in async modules

v5.3.1

Compare Source